Skip to main content

Repository Management

Repository Management nima?​

Repository Management - bu Git repositorylaringizni tartibli, xavfsiz va samarali tarzda boshqarishdir.

Bu xuddi kutubxonani tartibda saqlash kabi - har bir kitob o'z joyida, topish oson, tartib-qoidalar bor! 📚

Repository Structure​

1. Standard Project Structure​

my-project/
├── .github/                    # GitHub specific files
│   ├── workflows/             # CI/CD workflows  
│   ├── ISSUE_TEMPLATE/        # Issue templates
│   └── PULL_REQUEST_TEMPLATE.md
├── .gitlab/                   # GitLab specific
│   └── merge_request_templates/
├── docs/                      # Documentation
│   ├── README.md
│   ├── API.md
│   └── DEPLOYMENT.md
├── src/                       # Source code
│   ├── components/
│   ├── services/
│   └── utils/
├── tests/                     # Test files
│   ├── unit/
│   ├── integration/
│   └── e2e/
├── docker/                    # Docker files
│   ├── Dockerfile
│   ├── docker-compose.yml
│   └── .dockerignore
├── k8s/                       # Kubernetes manifests
│   ├── deployment.yaml
│   ├── service.yaml
│   └── ingress.yaml
├── scripts/                   # Build/deployment scripts
│   ├── build.sh
│   ├── deploy.sh
│   └── test.sh
├── .gitignore                 # Git ignore rules
├── .env.example               # Environment template
├── package.json               # Dependencies (Node.js)
├── requirements.txt           # Dependencies (Python)
├── README.md                  # Project documentation
├── LICENSE                    # License file
└── CHANGELOG.md               # Version history

2. Monorepo Structure​

company-monorepo/
├── apps/                      # Applications
│   ├── web-app/
│   ├── mobile-app/
│   └── admin-panel/
├── packages/                  # Shared packages
│   ├── ui-components/
│   ├── utils/
│   └── api-client/
├── services/                  # Microservices
│   ├── user-service/
│   ├── payment-service/
│   └── notification-service/
├── infrastructure/            # DevOps files
│   ├── terraform/
│   ├── ansible/
│   └── k8s/
└── tools/                     # Development tools
    ├── linting/
    ├── testing/
    └── ci-cd/

Repository Configuration​

1. Git Configuration​

Global config:​

# User information
git config --global user.name "Sizning Ismingiz"
git config --global user.email "email@company.com"

# Editor
git config --global core.editor "code --wait"

# Default branch
git config --global init.defaultBranch main

# Helpful aliases
git config --global alias.st status
git config --global alias.co checkout
git config --global alias.br branch
git config --global alias.unstage "reset HEAD --"
git config --global alias.last "log -1 HEAD"
git config --global alias.visual "!gitk"

Repository config:​

# Local repository settings
git config user.email "work@company.com"
git config core.autocrlf false
git config core.filemode false

2. .gitignore Configuration​

Node.js project:​

# Dependencies
node_modules/
npm-debug.log*
yarn-debug.log*
yarn-error.log*

# Runtime data
pids
*.pid
*.seed
*.pid.lock

# Directory for instrumented libs
lib-cov

# Coverage directory used by tools like istanbul
coverage/
*.lcov

# nyc test coverage
.nyc_output

# Dependency directories
jspm_packages/

# Optional npm cache directory
.npm

# Optional eslint cache
.eslintcache

# Microbundle cache
.rpt2_cache/
.rts2_cache_cjs/
.rts2_cache_es/
.rts2_cache_umd/

# Optional REPL history
.node_repl_history

# Output of 'npm pack'
*.tgz

# Yarn Integrity file
.yarn-integrity

# dotenv environment variables file
.env
.env.test
.env.local
.env.production

# Build outputs
dist/
build/

# IDE files
.vscode/
.idea/
*.swp
*.swo
*~

# OS generated files
.DS_Store
.DS_Store?
._*
.Spotlight-V100
.Trashes
ehthumbs.db
Thumbs.db

Python project:​

# Byte-compiled / optimized / DLL files
__pycache__/
*.py[cod]
*$py.class

# C extensions
*.so

# Distribution / packaging
.Python
build/
develop-eggs/
dist/
downloads/
eggs/
.eggs/
lib/
lib64/
parts/
sdist/
var/
wheels/
*.egg-info/
.installed.cfg
*.egg
MANIFEST

# PyInstaller
*.manifest
*.spec

# Installer logs
pip-log.txt
pip-delete-this-directory.txt

# Unit test / coverage reports
htmlcov/
.tox/
.nox/
.coverage
.coverage.*
.cache
nosetests.xml
coverage.xml
*.cover
.hypothesis/
.pytest_cache/

# Virtual environments
venv/
ENV/
env/
.venv/

# IDE
.vscode/
.idea/
*.swp
*.swo

# Environment variables
.env
.env.local
.env.production

3. Git Hooks​

Pre-commit hook:​

#!/bin/sh
# .git/hooks/pre-commit

echo "🔍 Running pre-commit checks..."

# Check for debugging statements
if grep -r "console.log\|debugger\|pdb.set_trace" src/; then
    echo "❌ Debug statements found. Please remove them."
    exit 1
fi

# Run linting
echo "🧹 Running linter..."
npm run lint
if [ $? -ne 0 ]; then
    echo "❌ Linting failed. Please fix the issues."
    exit 1
fi

# Run tests
echo "🧪 Running tests..."
npm test
if [ $? -ne 0 ]; then
    echo "❌ Tests failed. Please fix the tests."
    exit 1
fi

echo "✅ All pre-commit checks passed!"
exit 0

Commit-msg hook:​

#!/bin/sh
# .git/hooks/commit-msg

# Check commit message format
commit_regex='^(feat|fix|docs|style|refactor|test|chore)(\(.+\))?: .{1,50}'

if ! grep -qE "$commit_regex" "$1"; then
    echo "❌ Invalid commit message format!"
    echo "Format: type(scope): description"
    echo "Example: feat(auth): add login functionality"
    echo ""
    echo "Types: feat, fix, docs, style, refactor, test, chore"
    exit 1
fi

echo "✅ Commit message format is valid!"

Access Control va Permissions​

1. GitHub Repository Settings​

Collaborators management:​

# .github/settings.yml
repository:
  name: my-project
  description: Project description
  homepage: https://example.com
  topics: [javascript, react, nodejs]
  private: false
  
  # Features
  has_issues: true
  has_projects: true
  has_wiki: false
  has_downloads: true
  
  # Settings
  default_branch: main
  allow_squash_merge: true
  allow_merge_commit: false
  allow_rebase_merge: true
  delete_branch_on_merge: true

# Branch protection
branches:
  - name: main
    protection:
      required_status_checks:
        strict: true
        contexts: [ci/tests, ci/build]
      enforce_admins: true
      required_pull_request_reviews:
        required_approving_review_count: 2
        dismiss_stale_reviews: true
        require_code_owner_reviews: true
      restrictions:
        users: []
        teams: [team-leads]

Teams va permissions:​

# Team structure
teams:
  - name: backend-team
    permission: push
    members:
      - dev1
      - dev2
  
  - name: frontend-team  
    permission: push
    members:
      - dev3
      - dev4
      
  - name: devops-team
    permission: admin
    members:
      - devops1
      - devops2

2. CODEOWNERS File​

# .github/CODEOWNERS

# Global owners
* @team-leads @senior-developers

# Frontend
/frontend/ @frontend-team
*.js @frontend-team
*.vue @frontend-team
*.css @ui-designers

# Backend  
/backend/ @backend-team
*.py @backend-team
*.go @backend-team

# DevOps
/docker/ @devops-team
/k8s/ @devops-team
/.github/workflows/ @devops-team
/terraform/ @infra-team

# Documentation
/docs/ @tech-writers @team-leads
README.md @team-leads

# Configuration
*.json @backend-team @devops-team
*.yaml @devops-team
*.yml @devops-team

# Database
/migrations/ @database-team @backend-team
*.sql @database-team

Repository Templates​

1. GitHub Template Repository​

Template yaratish:

# Template repository settings
Settings → Template repository ✅

# Template structure
template-repo/
├── .github/
│   ├── workflows/
│   │   ├── ci.yml
│   │   └── cd.yml
│   ├── ISSUE_TEMPLATE/
│   │   ├── bug_report.md
│   │   └── feature_request.md
│   └── PULL_REQUEST_TEMPLATE.md
├── src/
├── tests/
├── .gitignore
├── README.md
└── package.json

2. Issue Templates​

<!-- .github/ISSUE_TEMPLATE/bug_report.md -->
---
name: Bug Report
about: Create a report to help us improve
title: '[BUG] '
labels: bug
assignees: ''
---

## 🐛 Bug Description
A clear description of what the bug is.

## 🔄 Steps to Reproduce
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

## ✅ Expected Behavior
What you expected to happen.

## ❌ Actual Behavior  
What actually happened.

## 📱 Environment
- OS: [e.g. macOS, Windows, Linux]
- Browser: [e.g. Chrome, Safari]
- Version: [e.g. 22]

## 📎 Additional Context
Add any other context about the problem here.

3. Pull Request Template​

<!-- .github/PULL_REQUEST_TEMPLATE.md -->
## 📝 Description
Brief description of changes made.

## 🔗 Related Issue
Fixes #(issue number)

## 🧪 Testing
- [ ] Unit tests pass
- [ ] Integration tests pass  
- [ ] Manual testing completed

## 📋 Checklist
- [ ] Code follows style guidelines
- [ ] Self-review completed
- [ ] Documentation updated
- [ ] No breaking changes
- [ ] Tests added/updated

## 📸 Screenshots (if applicable)
Add screenshots here.

## 🚀 Deployment Notes
Any special deployment considerations.

Repository Maintenance​

1. Regular Cleanup​

Delete merged branches:​

# Local branches cleanup
git branch --merged main | grep -v main | xargs -n 1 git branch -d

# Remote branches cleanup  
git remote prune origin

# Delete local tracking branches
git branch -vv | grep ': gone]' | awk '{print $1}' | xargs git branch -D

Large files cleanup:​

# Find large files
git rev-list --objects --all | 
  git cat-file --batch-check='%(objecttype) %(objectname) %(objectsize) %(rest)' |
  sed -n 's/^blob //p' |
  sort --numeric-sort --key=2 |
  tail -10

# Remove large files from history
git filter-branch --tree-filter 'rm -f large-file.zip' HEAD
git push origin --force --all

2. Archive Strategy​

# Repository lifecycle
active: 2 years
maintenance: 1 year  
archived: indefinite

# Archive checklist:
- [ ] Final documentation update
- [ ] Dependencies security scan
- [ ] Backup important data
- [ ] Update README with archive notice
- [ ] Set repository to read-only

3. Backup Strategy​

# Automated backup script
#!/bin/bash

BACKUP_DIR="/backups/git-repos/$(date +%Y-%m-%d)"
mkdir -p "$BACKUP_DIR"

# Clone with all branches and tags
git clone --mirror git@github.com:company/repo.git "$BACKUP_DIR/repo.git"

# Backup issues and PRs (GitHub API)
curl -H "Authorization: token $GITHUB_TOKEN" \
  "https://api.github.com/repos/company/repo/issues?state=all" \
  > "$BACKUP_DIR/issues.json"

# Compress backup
tar -czf "$BACKUP_DIR.tar.gz" "$BACKUP_DIR"

Repository Analytics​

1. Metrics Tracking​

# Commit frequency
git log --oneline --since="1 month ago" | wc -l

# Contributors
git shortlog -sn --since="1 month ago"

# Code churn
git log --stat --since="1 month ago" | grep "file changed" | 
  awk '{added+=$4; deleted+=$6} END {print "Added: " added " Deleted: " deleted}'

# Most active files
git log --name-only --pretty=format: | sort | uniq -c | sort -nr | head -10

2. Health Monitoring​

# Repository health checks
health_check:
  - recent_commits: true
  - active_contributors: > 2
  - test_coverage: > 80%
  - security_vulnerabilities: 0
  - outdated_dependencies: < 5
  - documentation_updated: < 30_days

Multi-Repository Management​

1. Git Submodules​

# Add submodule
git submodule add https://github.com/company/shared-lib.git lib/shared

# Initialize submodules
git submodule init
git submodule update

# Update submodules
git submodule update --remote

# Clone with submodules
git clone --recursive https://github.com/company/main-project.git

2. Git Subtrees​

# Add subtree
git subtree add --prefix=lib/shared https://github.com/company/shared-lib.git main

# Update subtree
git subtree pull --prefix=lib/shared https://github.com/company/shared-lib.git main

# Push changes back
git subtree push --prefix=lib/shared https://github.com/company/shared-lib.git main

3. Monorepo Tools​

// lerna.json
{
  "version": "independent",
  "npmClient": "npm",
  "command": {
    "publish": {
      "conventionalCommits": true
    },
    "bootstrap": {
      "ignore": "component-*",
      "npmClientArgs": ["--no-package-lock"]
    }
  },
  "packages": ["packages/*"]
}

Best Practices​

1. Security​

  • ✅ Repository secrets scan qiling
  • ✅ Branch protection rules o'rnating
  • ✅ 2FA enable qiling
  • ✅ Access permissions regularly review qiling
  • ✅ Sensitive data ni environment variables da saqlang

2. Organization​

  • ✅ Consistent naming conventions ishlatang
  • ✅ Clear documentation yozing
  • ✅ Regular cleanup qiling
  • ✅ Archive old repositories
  • ✅ Template repository yarating

3. DevOps Integration​

  • ✅ CI/CD pipeline sozlang
  • ✅ Automated testing qo'shing
  • ✅ Quality gates o'rnating
  • ✅ Monitoring va alerting sozlang
  • ✅ Backup strategy implement qiling

Xulosa​

Repository Management - bu dasturlash loyihasining poydevoridir:

✅ Organization - tartibli tuzilish ✅ Security - xavfsiz access control
✅ Collaboration - samarali hamkorlik ✅ Maintenance - doimiy parvarish ✅ Automation - avtomatik jarayonlar

DevOps engineer sifatida repository managementni yaxshilash orqali butun development lifecycle ni optimize qilishingiz va jamoangizning productivligini oshirishingiz mumkin!